NTISthis.com

Evidence Guide: ICTTEN7220A - Translate domain and solution architectures into platform requirements and designs

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTTEN7220A - Translate domain and solution architectures into platform requirements and designs

What evidence can you provide to prove your understanding of each of the following citeria?

Develop system design requirements

  1. Produce a system requirements specification for a complex project involving enterprise and technology issues using the simplest possible technology and making the system modular
  2. Resolve and negotiate requirement conflicts in order to establish a complete and consistent requirement set
  3. Produce and develop acceptance criteria for requirements
  4. Design a requirements management plan with categorisations, structures and sources of complexity
  5. Develop a process to manage the requirements enabling users to influence future improvements
Produce a system requirements specification for a complex project involving enterprise and technology issues using the simplest possible technology and making the system modular

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Resolve and negotiate requirement conflicts in order to establish a complete and consistent requirement set

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce and develop acceptance criteria for requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Design a requirements management plan with categorisations, structures and sources of complexity

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop a process to manage the requirements enabling users to influence future improvements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce system design based on requirements

  1. Evaluate the strengths and weaknesses of relevant technologies in the context of the design requirement and needs for systems integration
  2. Create a range of alternative interdisciplinary concepts and assess their attributes
  3. Plan for the incorporation of later life cycle design attributes in developing the design requirements
  4. Devise a system design strategy and approach and use the tools and techniques to conduct functional analysis
  5. Produce a set of parameters to track critical aspects of the design
  6. Use documentation, modelling and simulation tools and techniques to represent a system or system element
  7. Use complex simulations to evaluate design concepts for a system or system element
  8. Produce a report to evaluate and advise on the risks, suitability and limitations of models and simulations
  9. Identify the underlying domain specific issue, strategy and approach to be adopted for ensuring system robustness
  10. Produce a robust design using domain specific strategy and approach to platform requirements and designs
Evaluate the strengths and weaknesses of relevant technologies in the context of the design requirement and needs for systems integration

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Create a range of alternative interdisciplinary concepts and assess their attributes

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Plan for the incorporation of later life cycle design attributes in developing the design requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Devise a system design strategy and approach and use the tools and techniques to conduct functional analysis

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce a set of parameters to track critical aspects of the design

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Use documentation, modelling and simulation tools and techniques to represent a system or system element

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Use complex simulations to evaluate design concepts for a system or system element

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce a report to evaluate and advise on the risks, suitability and limitations of models and simulations

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify the underlying domain specific issue, strategy and approach to be adopted for ensuring system robustness

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Produce a robust design using domain specific strategy and approach to platform requirements and designs

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Verify solution design and traceability

  1. Determine specific aspects of the design to the original intent
  2. Verify and track specific aspects of the current design back to the original intent throughout the supply chain
  3. Trace verification requirements back to system requirements and vice versa
  4. Use change control and configuration management to implement remedial actions and change control of inconsistencies
Determine specific aspects of the design to the original intent

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Verify and track specific aspects of the current design back to the original intent throughout the supply chain

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Trace verification requirements back to system requirements and vice versa

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Use change control and configuration management to implement remedial actions and change control of inconsistencies

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to:

develop system design requirements

evaluate design concepts for system or system element using complex simulations

produce a system design using domain specific strategy to platform requirements and design

use functional analysis tools

use complex simulations

verify solution design and traceability.

Context of and specific resources for assessment

Assessment must ensure:

a site where development, deployment, management and optimisation of domain and solution architectures into platform requirements and designs can be undertaken

documentation, modelling and simulation tools currently used in industry

tests and equipment currently used in industry.

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:

direct observation of the candidate translating domain and solution architectures into platform requirements and designs

oral and written questioning of the candidate to assess required knowledge of platform requirements and designs

review of the candidate's documented simulation testing and change and improvement recommendations.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, for example:

ICTTEN7222A Manage solution architecture and impacts in line with organisational processes.

Aboriginal people and other people from a non-English speaking background may have second language issues.

Access must be provided to appropriate learning and assessment support when required.

Assessment processes and techniques must be culturally appropriate, and appropriate to the oral communication skill level, and language and literacy capacity of the candidate and the work being performed.

In all cases where practical assessment is used it will be combined with targeted questioning to assess required knowledge. Questioning techniques should not require language, literacy and numeracy skills beyond those required in this unit of competency.

Where applicable, physical resources should include equipment modified for people with special needs.

Required Skills and Knowledge

Required skills

communication skills to liaise with internal and external personnel on technical and operational matters

information technology skills for:

desktop research

enabling production of a system requirements specification for a complex project

word processing

literacy skills to:

interpret technical documentation such as software and hardware manuals and specifications

interpret relevant enterprise policy and documentation

prepare reports given a specific format

read and comply with related occupational health and safety (OHS) requirements and work practices

numeracy skills to take and analyse measurements

planning and organisational skills to:

break large projects into a series of small projects

organise testing and contingency plans

problem solving skills to manage and trace technical margins both horizontally and vertically through the hierarchy

task management skills to work systematically with required attention to detail and adherence to project requirements

technical skills to:

conduct functional analysis

create design solutions

use simulation software

Required knowledge

complex simulation techniques

current enterprise platforms and designs

design of management plans

domain and solution architectures

enterprise and technology issues

information required to simulate computer system elements according to a test specification

interdisciplinary concepts and attributes

life cycle design attributes

remedial actions and change control of inconsistencies

solution design and traceability

tools to conduct functional analysis

Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Enterprise and technology issues may include:

communication and interoperability issues

distributed enterprise applications

technologies you deploy

vendors you select as partners.

Sources of complexity may include:

different domains

multinational programmes

multiple suppliers

novel technology.

Systems integration may include:

combining component subsystems into one system and ensuring that the subsystems function together as a system

process of linking together different computing systems and software applications physically or functionally.

Interdisciplinary concepts may include:

behaviour

functionality

structure.

Attributes may include:

availability

cost

feasibility

human factors

maintainability

reliability

risk

schedule

technology requirements

testability.

Life cycle design attributes may include:

availability

maintainability

reliability

testability.

Functional Analysis component functions may include:

accounting

manufacturing

marketing

product design

sales.

System element may include:

elements that can support several interfaces

requirements posed on the system element

services to be provided by the system element

specified connected devices and interfaces.